Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(JumpLinks): warned about href and markup/type updates #575

Merged
merged 4 commits into from
Feb 26, 2024

Conversation

thatblindgeye
Copy link
Collaborator

Closes #559

Copy link
Collaborator

@wise-king-sullyman wise-king-sullyman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple non-blocking comments

@@ -16,6 +16,7 @@ export const warningRules = [
"emptyState-warn-change-structure",
"formControls-updated-markup",
"horizontalSubnav-warn-ariaLabel",
"jumpLinksItem-warn-prop-markup-updates",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if this should really be a warning since the href now being required will throw build errors.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that's fair. I'll split that out to its own rule since the markup change should probably still remain a warning.

@@ -0,0 +1 @@
import { JumpLinksItem } from "@patternfly/react-core";
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could these tsx files be deleted?

Copy link
Collaborator Author

@thatblindgeye thatblindgeye Feb 26, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think they'd be worth keeping in, just so that running the single tests locally we can still check that the output looks as expected (mainly warning vs error). They might be able to be used to create a mass test file where all the rules' input code is rendered to ensure no rules conflict with one another?

Testing it out, though, the single test command throws an error due to no input/output file being found. The script to build the readme also fails without them.

@wise-king-sullyman wise-king-sullyman merged commit 0af1541 into patternfly:main Feb 26, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Jump Links - Penta updates
2 participants